Nways Manager-LAN provides a variety of submaps that display detailed views of the network resources you are managing. The top-level, or Root submap, displays icons representing the communication protocols and IBM hubs used in your network.
From the Root submap, you can navigate through hierarchies of submaps to manage your network resources. Each submap provides an increasingly detailed view of network resources.
To manage network resources that use other communication protocols, such as IP or SNA, double-click on the appropriate protocol icon in the Root submap. This allows you to access the submap hierarchies provided by NetView for AIX and other AIX applications.
| Note: | To configure SNMP parameters for hub agents, select Options -> SNMP Configuration from the menu bar of the Root Submap. Any changes you make to hub agents are displayed in the Configuration panels for the corresponding hub view. |
Nways Manager-LAN displays the following views for managing your 8250, 8260, 8265, PSM-managed, and Java web-managed devices:
To move between different views, double-click the left mouse button on an object in the view. For example, start from the IBM Hubs Topology, double-click on a hub to explode the hub and display a Hub Level view. In the Hub Level view, double-click on the icon of a module to explode the module and display a Module Level view.
Each type of hub view is described in the following sections.
After you double-click on the IBM Hubs Topology icon in the Root submap, the IBM Hubs Topology is displayed. This view displays all the 8250, 8260, 8265, and PSM-managed and Java web-managed devices with the inter-hub links in the network that you manually added.
New hubs are placed in the submap as soon as they are discovered.
You can explode a hub only when the hub is managed. For managed hubs, all menu items and configuration panels for the hub are available. If the polling policy is regular, the hub is polled according to the number of seconds configured for its polling interval. The hub symbol in the IBM Hubs Topology changes color to reflect changes in hub status as reported by the poll.
To manage one or more hubs:
An unmanaged hub is not managed by Nways Manager-LAN. This means that the hub is not polled despite the polling policy (for example, regular) that is currently configured. All configuration panels are disabled and the Hub Level view cannot be opened. The hub icon in the IBM Hubs Topology does not report the hub's status because it is not known. The hub icon, however, remains visible.
To unmanage one or more hubs:
When the next poll is performed, the hub is discovered as unmanaged and is polled once. The hub, however, remains in the unmanaged state. No menu options are available on its context menu.
To manage or unmanage all hubs in the IBM Hubs Topology:
8250, 8260, 8265, PSM-managed, and Java web-managed devices are executable when there is a square, three-dimensional frame around their icons in the IBM Hubs Topology.
If an error message is displayed the first time you double-click on a PSM-managed icon, this means that you have not yet registered the device to the Management Application Transporter. To do so, follow these steps:
For more information on using the Management Application Transporter, refer to the documentation stored in /usr/lpp/mgtapptran/doc. To display online help for a particular PSM, enter the following command:
/usr/lpp/mgtapptran/bin/viewDoc docname
where docname is the name of the online document (for example, R8224UG).
| Note: | If you double-click on a hub icon that is not executable (that does not have the three-dimensional square frame around it), the NetView for AIX view of the hub's interfaces is displayed. See the NetView for AIX User's Guide for more information. |
Each type of hub managed by Nways Manager-LAN is displayed in the IBM Hubs Topology by an icon that represents the physical characteristics of the hub. For example, you can see icons for the following:
The icons used to represent each of these hubs are displayed either horizontally or vertically.
The Hub Level view displays the modules installed in a selected hub and is opened when you:
The status of modules is color-coded in compliance with NetView for AIX.
When you open a Hub Level view, a forced poll is performed.
A pop-up window is displayed if you open the Hub Level view for a hub that is in one of the following states:
Depending on whether the hub is an 8250, 8265, or an 8265 ATM switch, the number and type of icons displayed at the bottom of the view differs:
The hub temperature is not necessarily related to the status of the fans. It reflects the overall temperature as collected by the various temperature probes.
A special icon is displayed to identify broken connections. When this icon appears, the corresponding hub icon becomes red in the Network Level View. When a connection no longer exists with a hub, you can still expand the hub by double-clicking on the hub icon and displaying the Hub Level View. The information displayed is the last known configuration of the hub. A logo is displayed that reflects the chassis's type.
Double-clicking on the icon above a module in the Hub Level view or selecting Open View from the module's context menu displays the Module Level view.
To display information about a color-coded hub resource, click MB1 on an icon. Information about the resource and polling information are displayed in the Information area at the bottom of an expanded Hub Level View.
If the resource is configured for Regular Polling, the polling interval set in the Polling Policy panel is displayed with the date and time of the previous poll. If the resource is configured for Polling on Request, the date and time of the previous poll is displayed.
Using the Network area on the right side of an expanded Hub Level View, you can list the network segments attached to the hub according to network type. To do so, click MB1 on one of the Network icons. For example, if you click on Token-Ring, a second box opens showing the Token-Ring segments attached to the hub.
To highlight the hub resources assigned to a specific network, click MB1 on one of the icons in the second box. All other resources, except for fans, power supplies, temperature, PS/2, and power distribution boards, are displayed in reduced highlight.
To redisplay all highlighted hub resources, click on the Show All button. To display the context menu for a network segment, click MB3 on one of the Network icons in the second box.
Also, you can use the Network area as a drop site for assigning hub resources to a network segment. To do so, drag an icon (for example, a port) in the Hub Level view and drop it on the icon of a network segment.
Unrecognized modules installed in 8250 and 8260 hubs and 8265 ATM switches are displayed in a Hub Level view and are represented by the icon for Unrecognized Module shown in the Legend panel.
There are three categories of unrecognized modules:
You can perform a limited set of management functions on unrecognized modules and view only a limited amount of configuration information:
Modules installed in 8250 and 8260 hubs and 8265 ATM switches may be managed in a generic way and are represented by the icon for Generic Support.
Modules may be generically supported for either of the following reasons:
The generic functions that you can perform on these modules are as follows:
Note that in a Hub Level view:
The Module Level view displays an expanded view of the selected module. It provides module-specific information and information about the devices attached to the module.
The Module Level view is dynamically updated according to the MAC address polling policy when stations are moved, added, or removed.
The Module Level view contains:
| Note: | The module is shown either horizontally or vertically depending on the type of chassis. |
These ports and trunks are the same as those shown in the unexpanded view of the module including the same port menu structure and the same status. For modules which contain banks, all the banks are automatically expanded to show all the ports they contain.
Notes:
A line is shown between the device icon and the port it is connected to, representing the connection between the port and the device.
You can associate names to different devices to help in problem determination and to easily locate resources using the Search function.
You can display other views associated with the device by double-clicking on the device icon. The status of the ports is updated when the corresponding port status is updated in the Hub Level view. There is no particular relationship between port status and station status. The device status is the status reported by either the 8250, 8260, and 8265 Device Manager or (if installed) the LAN Network Manager application of Nways Manager-LAN.
The network icon representing the type of protocol used in the LAN segment is displayed in the bottom righthand corner. To open the submap of the segment managed by the module, select LAN from the icon's context menu.
In the Module Level view of a Bridge module, the network icon representing the type of protocol used in the LAN subnet is displayed in the bottom righthand corner. To open the submaps in which the bridge is displayed, select LAN from the icon's context menu.
You can open the Nways Manager-ATM view of the ATM cluster managed by the A-CPSW switch by selecting Open Device from the icon's context menu.
Nways Manager-LAN displays the following submaps for managing your LAN resources:
To navigate from one submap to another, double-click on an explodable icon that represents a network resource. Double-clicking on an explodable icon opens a submap associated with the icon. For example, if you double-click on a segment icon in a LAN Subnet submap, a Segment submap for the selected segment is displayed.
The following sections describe the hierarchy of LAN submaps used in Nways Manager-LAN.
After you double-click on the LAN icon in the Root submap, the LAN Network submap is displayed. This submap displays the subnets managed by the LAN Network Manager application of Nways Manager-LAN.
The naming conventions used in the LAN names below each icon are as follows:
When a segment is managed by a token-ring RMON agent, the name is in the format: RMON <agent_IP_address>-<segmentIndex>
When a segment is managed by a token-ring 8230 agent, the name is in the format: CAU <agent_IP_address>
When a segment is managed by a token-ring surrogate agent, the name is in the format: <surrSegmentNumber>
When a segment is managed by an FDDI proxy agent, the name is in the format: <agent_IP_address>-<segmentIndex>
For some types of LAN subnets, you can select the subnet icon and then select Configuration from the LAN pull-down menu to display and change configuration parameters. From the LAN Network submap, you can also double-click on a subnet icon to open the LAN Subnet submap that displays the network resources in the subnet.
Notes:
/usr/CML/bin/cmlstatus lnmbrmon
The LAN Subnet submap provides a detailed view of a selected subnet. The different types of LAN segments (token-ring, FDDI, and Ethernet) and the bridges and switches that connect them are represented with icons.
You can display the resources in a particular segment by double-clicking on a segment icon to open a Segment submap.
You can display the ports and attached segments of a particular bridge by double-clicking on the bridge icon to open a Bridge submap.
The LAN Subnet submap can display segment icons for LLC token-ring, SNMP token-ring, and FDDI segments. If the stations on a segment have been discovered, you can double-click on the segment icon to open a Segment submap.
Other segment types, such as Ethernet, X.25, and Frame-Relay, can also be represented by icons in the LAN Subnet submap, but because they are not managed by the LAN Network Manager application, you cannot display a Segment submap for these types of segments.
For LLC token-ring, SNMP token-ring, and FDDI segments, the Segment submap shows a detailed view of the resources on a specific segment. Stations, bridges, and concentrators are represented by icons placed around a ring. Stations that are operating a proxy agent program, such as the OS/2 agent or the FDDI SNMP Proxy Agent, are displayed with a oval icon to distinguish them from other stations, which are represented by square or diamond-shaped icons.
The Segment submap for LLC token-ring segments shows the stations, bridges, and 8230 Model 1 and Model 2 concentrators on the selected segment, displayed in nearest active upstream neighbor (NAUN) order, according to their adapters. (Adapters integrated in an 8230 Model 1 or Model 2 concentrator are not displayed in the Segment submap; they are displayed in the Concentrator submap.)
The Segment submaps for FDDI and SNMP token-ring segments are similar to the Segment submap for LLC token-ring segments. Stations, bridges, and concentrators are displayed in NAUN order clockwise, according to their MAC addresses.
Note that the station 08005ADB0044 has an oval icon to indicate that the station is running the proxy agent program.
From any type of LAN Segment submap, you can determine the current status of a resource by its color, obtain profile, configuration, fault, and performance information for a resource, and navigate to a Node, Bridge, or Concentrator submap for a detailed view of a particular resource.
For FDDI networks, you can open an FDDI Station submap to display the managed elements of an FDDI station. To do so, double-click on an FDDI station in an FDDI Segment submap. The FDDI Station submap opens to display a graphical representation of a computer workstation. Icons representing the SMT, attachment, MAC, path, path class, and ports are displayed in the submap.
From the FDDI Station submap, you can determine the current status of a resource by its color, and obtain profile, configuration, fault, and performance information for a resource. You can also double-click on the MAC icon to open a Node submap for the selected station.
The Node submap displays icons that represent the contents of a station or a bridge port, according to protocol. Each Node submap contains one or more icons: one icon to represent the selected station or bridge port, and one icon to represent each protocol present in the station or bridge port.
From the Node submap, you can determine the current status of a resource by its color, and obtain profile, configuration, fault, and performance information for a resource.
Nways Manager-LAN uses a Bridge submap to represent bridges, such as the IBM 8229 and 8250. The Bridge submap displays a graphical representation of the bridge, with icons representing the bridge port interfaces, the segments to which the bridge is attached, and the bridge itself.
From the Bridge submap, you can determine the current status of each bridge port interface by its color, and obtain profile, configuration, fault, and performance information for these elements using the management windows. Double-clicking on the icons that represent a bridge port interface opens a Node submap for the bridge port.
| Note: | In Bridge submaps, realistic views of SNMP bridges have been replaced by a generic view that allows you to represent multiple segments on the same interface. Realistic views are still available by double-clicking on the bridge icon to start the Product Specific Module. |
To represent the IBM 8230 Model 1 and Model 2, the IBM 8240 and 8244 concentrators, and generic FDDI concentrators, Nways Manager-LAN uses a Concentrator submap.
The Concentrator submap displays a graphical representation of the concentrator itself. Points of attachment and other physical features of the hardware are recognizable in the submap, and all managed elements of the concentrator are represented by icons. The icons give you access to the managed elements of the device and to the stations inserted into the device.
For the SNMP-managed IBM 8230, Nways Manager-LAN invokes the Product Specific Management applications. Online documentation of applications associated with these devices can be viewed by entering
/usr/lpp/mgtapptran/bin/viewDoc <docname>
where docname is the name of the online documentation that you want to view.
In Nways Manager-LAN, you can switch between any of the following views according to the protocols that are running in a selected hub or LAN resource:
To switch between different protocol views of a network resource,
Nways Protocols allows you to switch between the following submaps: IP Internet submap, Nways Manager-ATM, LAN, or hub view.
For example, if you switch to a view of a hub according to its IP address, a submap is displayed.
From the IBM Hubs Topology view and IP and LAN submaps, you can manage network resources in the following ways:
Note that you can also select operations from the context menu of a selected hub. To display a context menu, click the right mouse button (MB3) on a resource icon.
To navigate between hub or module views and LAN submaps, do one of the following:
| Note: | Navigation between LAN submaps and hub views is not supported for token-ring segments discovered by the LNM OS/2 proxy agent. |
Nways Manager-LAN receives information from a variety of sources in the network, such as SNMP proxy agent programs and SNMP bridges. In many cases an agent can operate in the same LAN environment as another agent and not be aware of the other agent's function. Nways Manager-LAN processes information from both agents, building separate topological submaps of the agent-reported resources.
To create a more accurate depiction of the network, Nways Manager-LAN checks for this kind of overlap, and if the program discovers a match, it merges the submaps that are represented through the respective agents into a single submap. When this happens, it is common for a duplicate icon that represents a merged segment to be removed from a higher-level submap. This does not mean you lose access to the merged resources; the updating of the submaps simply provides a cleaner and more comprehensive navigation path to the resources in your network.
The merging process occurs automatically when Nways Manager-LAN detects a situation that requires it. Nways Manager-LAN records all merges in the event display.
| Note: | The reporting policy of each agent can be in canonical or non-canonical
format and may impact the automatic merging process that normally
occurs. You can change the format in which token-ring RMON agents
report their MAC address as follows:
|
For token-ring segments managed by different types of SNMP proxy agents, you may sometimes want to disable the discovery of one or more agents in the following situations:
For example, you may have dual reporting on the same token-ring segment if the following devices are running:
If the two submaps generated by the different agents do not merge, you can solve the problem by disabling one or more of the SNMP token-ring agents that report information about the segment.
To disable the discovery of a token-ring SNMP proxy agent:
/usr/CML/bin/cmlstop lnmtrmon /usr/CML/bin/cmlstart lnmtrmon
cml_agent_delete <agent_IP_address> cml_agent_add <agent_IP_address>
For more information, see the section "Configuring SNMP Agents that Manage Token-Ring Segments" in the online book Managing SNMP Token-Ring Resources and SNMP Bridges.
In your network, an SNMP bridge might be connected to segment 005, which is monitored by a token-ring SNMP proxy agent. Before merging takes place, the bridge and the segment are both represented in the LAN Network Submap by different icons. If you navigate to the LAN submap or the Bridge submap for the bridge, segment 005 is shown to be connected to the bridge, but the bridge cannot provide detailed information about the segment or its stations.
When performing management functions, Nways Manager-LAN matches the MAC address of one of the bridge's adapters with the MAC address of an active station reported on segment 005. Once this match is identified, Nways Manager-LAN merges the submaps that pertain to the bridge and segment 005. To accurately show the topology, Nways Manager-LAN moves the segment submap to the Bridge submap.
Now when you navigate to the LAN Subnet submap or Bridge submap, you can display the stations on segment 005 by double-clicking on the segment icon. Management functions for the bridge and segment are available from the same submap.
In this example, there might be two SNMP agents that are connected to segment 040 in your network. One is a token-ring SNMP surrogate agent residing in an IBM 8229 Bridge that is connected to the segment, and the other agent is a token-ring SNMP RMON agent that is running on a workstation connected to the segment. Both agents are providing Nways Manager-LAN with information about the segment and the stations of which they are aware. Before merging takes place, Nways Manager-LAN displays a subnet icon for each agent on the LAN Network submap. The LAN submaps show different views of the same segment, according to the management information supplied by each agent.
While correlating the list of MAC addresses in the network, Nways Manager-LAN matches the MAC addresses of stations reported by the token-ring surrogate agent with the MAC addresses of stations reported by the RMON agent. If there are less than 6 stations on a segment, Nways Manager-LAN matches all (100%) of those stations with stations on the other segment before initiating merging. If there are 6 or more stations on both segments, Nways Manager-LAN matches at least half (50%) of the stations before merging. After the matching conditions are met, Nways Manager-LAN merges the submaps that are related to the two agents by eliminating the icon that represents the RMON agent.
For the purpose of merging, Nways Manager-LAN always gives management priority to a token-ring surrogate agent, instead of an RMON agent, when both agents are present on the same segment. Segment 040 is now presented through a single icon, and the duplicate submaps are eliminated. In addition, only SNMP is managing the segment, eliminating duplicate traps and improving performance.
Although the secondary agent on the segment has been merged with the primary agent, the secondary agent still operates as a backup. If the primary agent loses connectivity, Nways Manager-LAN indicates this by changing the agent's status to Unknown and initiating an age-out timer. After you delete the agent, or after the age-out timer expires, the secondary agent assumes management and updates the Nways Manager-LAN submaps with its own information.
For example, suppose you have a token-ring surrogate agent and an RMON agent reporting on the same segment. Merging has already occurred, so the RMON agent's icon has been removed and merged with the token-ring surrogate's icon. If Nways Manager-LAN loses communication with the token-ring surrogate, and you delete the surrogate agent, a new Segment submap is created based on the RMON agent and its information about the stations on the segment.
To delete a token-ring surrogate agent, do one of the following:
For more information, see the online book Coupling and Autodiscovery.
In Nways Manager-LAN, icons (symbols) representing LAN resources are automatically positioned on submaps if the automatic layout is set to On. As new resources are discovered (for example, by polling information), new icons are added and the group of icons on the submap is automatically repositioned.
Nways Manager-LAN allows you, however, to customize the icon positions on Subnet, Segment, and Bridge submaps that display point-to-point connections (for example, a bridge connected to a segment). To do so, you must select a background for the submap by choosing Edit -> Select Background Picture from the menu bar. Then follow these steps:
| Note: | The Cut, Copy, and Paste functions in NetView for AIX are not supported. |
As new resources are discovered, their icons are placed in the New Object Holding area at the bottom of the submap. To position the new icons, use a mouse drag as described in Step 2.
After changing icon positions on a submap, you can restore the last saved positions by selecting View -> Nways -> Place Symbols Positions.
To delete the last saved positions for a submap, select View -> Nways -> Clear Symbol Position -> For This Submap.